"wolfc" wrote : A bean that has been looked up remotely, but that also exists locally should not be invoked locally. (Where local and remote are nodes which are not bound in the same cluster.) The behavior you describe is what existed for clustered beans looked up from a remote node: same cluster, go local, different cluster, go remote. I can reproduce that behavior with no problem w/ proxy-clustered. What's changed is the behavior of non-clustered beans -- before they went remote, now they go local. I found the threads related to EJBTHREE-773, and it's clear from those that the intent of Bill D's work was that the calls would go remote: http://www.jboss.com/?module=bb&op=viewtopic&t=104924 http://www.jboss.com/index.html?module=bb&op=viewtopic&t=101220 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172110#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...