The StatefulHandleImpl holds the jndiEnv after creation and uses these properties in getEJBObject.

Since jndiEnv is not transient, the properties used on client A are passed within the handle to Client B. This can lead to problems when these two clients use different properties (e.g. different host names for the same physical machine or a different implementation of the NamingContextFactory).

Example: client A resides on the JBoss server and realizes remote access to the server using localhost within his URL. A handle, created on this client and passed to client B, which resides on another machine, can not be used to get the EBJ object, since even this clients tries to connect to the server using a lookup on localhost.