From: <glassfish_at_javadesktop.org>
Date: Thu, 25 Mar 2010 07:08:52 PDT

There's no formal relationship between the GlassFish-specific global JNDI names and the EJB 3.1 specified portable JNDI names. GlassFish has always had its own proprietary global JNDI name scheme. That still applies in V3 for backward compatibility.

For those GlassFish-specific global JNDI names, a default name is only created if the Session bean exposes a single remote interface. The full rules are in the EJB FAQ : https://glassfish.dev.java.net/javaee5/ejb/EJB_FAQ.html#SessionBeanGlobalJNDINameAssignment

The GlassFish-specific(non-portable) and portable EJB 3.1 JNDI names use different namespaces, so there's no possibility for clashing. It just means in some cases there is more than one string that can resolve to a particular client view of a session bean. In fact, it's possible to create additional ones as well : http://blogs.sun.com/kensaks/entry/application_specified_portable_jndi_names
[Message sent by forum member 'ksak']

http://forums.java.net/jive/thread.jspa?messageID=393721