Thanks for answer.
BTW I managed to find solution before receiving your responce. One thing that was causing problem is misunderstanding the difference between JNDI global and environment naming context. As I have noticed this part is least covered in EJB3 related books, articles and tutorials. All these sources are more focused on simple scenarios without paying enough attention to cases I have.
Solution I come with is by putting mappedName attribute in Stateless annotation on EJB.
@Stateless(name="CountryBean", mappedName="ejb/Country")
also putting "ejb/" as prefix for mapped name automatically places it int "ejb/" jndi tree node in glassfish web admin's "Jndi tree browsing" window.
Also would like to pay attention in separating API classes from EJB implementation classes, and issues related with separate deployment of EJB, rar and war modules without putting them together in single ear. All samples I have red is leaving that question aside without bothering about covering this issue. Also there is not enough information about real deployment, updating, management strategies and issues.
If someone can provide links to information about issues listed above I'll be very thankful.
Regards Remis B
[Message sent by forum member 'remisb' (remisb)]
http://forums.java.net/jive/thread.jspa?messageID=242288