Optimizing for local calls is huge - avoiding the rmi call stack and the serialization is orders of magnitude faster. What if we went back to the original isLocalInterceptor mechanism and didn't use the ejbName to determine whether the bean was local? (we did the lookup in the EJB3Registry based on a unique name, so the isLocal() test would not get confused between a local instance of a bean vs a remote instance. The proxy has the container object name - what if we made that unique (add a VM specific or timestamp as a parameter of the container object name)?? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4027699#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...