I'm not aware of any but you can look for any general package naming recommendations rather than something EJB specific. The EJB specification does not impose any such requirements.
It's ok to have a bean class with the same package as its interface. From a client perspective just knowing the package name does not impose any particular coupling. It wouldn't prevent you from making only the interfaces available to the client if you wanted. In cases where you specifically intend to implement the same local or remote interface in two or more beans, there is some value in choosing different packages.
[Message sent by forum member 'ksak' (ksak)]
http://forums.java.net/jive/thread.jspa?messageID=244773