well first i would like to give u an idea about session beans. Session beans are used to manage the interactions of entity and other session beans, access resources, and generally perform tasks on behalf of the client. Session beans are not persistent business objects as are entity beans. They do not represent data in the database.
Stateless session beans, like all session beans, are not persistent business objects as are entity beans. They do not represent data in the database. Instead, they represent business processes or tasks that are performed on behalf of the client using them. The business methods in a stateless session bean act more like traditional procedures in a legacy transaction-processing monitor.
Stateful session beans are dedicated to one client and maintain conversational-state between method invocations. Unlike stateless session beans, clients do not share stateful beans. When a client creates a stateful bean, that bean instance is dedicated to service only that client. This makes it possible to maintain conversational-state, which is business state that can be shared by methods in the same stateful bean.