Hi,
This is one of the key thing to note in
EJB 3.0.
For both Local and Remote beans, when the bean object does not exist (for instance, this will happen if you try to invoke any business method on the stateful session bean after calling one of the @Remove method), the container will throw the javax.ejb.NoSuchEJBException. The only exception to this rule is when a @Remote Business interface also extends java.rmi.Remote, at this time, the container will throw java.rmi.NoSuchObjectException
Hope this helps.