posted 19 years ago
I believe it's because session beans can unset the context during the ejbRemove() call. Entity beans think of remove in a different way, ie., they delete the underlying entity from the persistent store. Thereforethey potentially need a way just to unset the context without relying on a remove.