Session beans are not persistent and you can remove the bean where in exactly bean gets removed so no context present. For entity beans its persistent on remove call you are removing the row from a table that is a persistent data. So if you have lot of entity beans in your pool which is over capacity for the system and that has to be reduced but remove cant be called so unsetEntityContext will be used to remove Context and release the entity bean from the pool to non existent state. There is no need of unsetSessionContext because there are no 2 case scenarios for ejbRemove for session beans unlike entity beans.
ok then.
regards
Narayanan
SCJP2 ,
SCEA (Part 1)