COPY from the guide for JBoss 4.0.3. It might be help. Not sure. "In JBoss 3.0.x, each client-side stub has its own list of available target nodes. Consequently, some side-effects can occur. For example, if you cache your home stub and re-create a remote stub for a stateless session bean (with the Round-Robin policy) each time you need to make an invocation, a new remote stub, containing the list of available targets, will be downloaded for each invocation. Consequently, as the first target node is always the first in the list, calls will not seemed to be load-balanced because there is no usage-history between different stubs. In JBoss 3.2+, the proxy families (i.e., the "First AvailableIdenticalAllProxies" load balancing policy, see Section 16.1.3.2) remove this side effect as the home and remote stubs of a given EJB are in two different families." View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4233497#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...