See also http://www.jboss.com/index.html?module=bb&op=viewtopic&t=135054 for related discussion. Scott's comment on that thread: anonymous wrote : I changed the JBoss5DeploymentScope to use an empty "" base name if the deployment is not an ear, so that should help with legacy expectations for the jndi name. leads me to think the extra data in the ObjectName can be avoided by checking for a null base name. Pretty arcane way to discriminate though. Getting rid of the extra data is a good thing to do, as the ObjectName forms the container's id, which is transmitted as invocation metadata with every remote request. For persistence units with JBC as a 2nd level cache, a similar approach to building a unique name is used in the JBC FQN for the cache region -- which again gets sent over the wire with any cache change messages. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157035#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...