Clients use the create and remove methods on the home interface of a stateless session bean in the
same way as on a stateful session bean. To the client, it appears as if the client controls the life cycle of
the session object. However, the container handles the create and remove calls without necessarily
creating and removing an EJB instance.
When does a stateless session bean client ever use "remove" on the home interface(of the stateless session bean)?What the point of doing that when control of creating and removing a stateless session bean is in the hand of the container?
I basically wanted to know ,when a client would ever call remove on a stateless session bean (seeing that that's what the spec says in that quote)
Of course: When you code EJB and client you know what kind of SessionBean you're using. But more often this is not the case, especially in bigger projects with strictly divided roles.