The main idea (from "ejb3 in action") is stateless session beans are the beans which are not able to maintain conversational state.
As you may know stateless session beans are pooled and when a client invokes any method the container takes an instance of stateless session bean and then invokes this method. And it doesn't matter which exactly instance is chosen to invoke.
hi Alexey... Thanks a lot. I got it..
So in case of STATEFUL session bean, container must invoke the same bean object which has
saved the conversational state between the client & server. Please correct me if I am wrong.