It's up to the deployer to assign a global JNDI name for a particular Remote EJB. By default, in Glassfish, the global JNDI name does indeed default to the fully qualified name of the Remote interface. However, the deployer can set that global JNDI name to anything, so there's no guarantee that the client can discover the appropriate target Remote EJB knowing only the interface name.
There could be multiple applications deployed to the same appserver that happen to have EJBs with the same interface name. These are all considered completely distinct and it's up to the deployer to assign global JNDI names for each that do not clash.
[Message sent by forum member 'ksak' (ksak)]
http://forums.java.net/jive/thread.jspa?messageID=253852