The change to determineLocalJndiName to drop the unique System.identityHashCode portion won't be valid for ejb2 deployments where there are multiple ejb jars that have the same ejb-names for beans with local interfaces, or mdbs. The same problem should exist for ejb3 as well doesn't? How are two standalone ejb3 jars each with a LocalBean going to share the same LocalBean/local global binding? I need to look at the tests to see what the issue is. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151903#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...