[ https://issues.jboss.org/browse/CDI-730?page=com.atlassian.jira.plugin.sy... ] Mark Struberg commented on CDI-730: ----------------------------------- I understand the argument that the order is really hard to get right. But I would love if we could clarify the following: * When a request ends, first ALL the @BeforeDestroyed events for the following contexts are sent: RequestScope, ConversationScoped (if context ends), SessionScoped (if session ends) * Only after that the proper @PreDestroy methods are called on all those scopes. PS: the deferral of the session destroy to the end of the request is a left over of the (failed) Seam2 compatibility mode. It should have never be done that way and really causes tons of problems :( In OWB there is even a way to turn this off and make it follow the standard Servlets Sesion lifecycle because it caused so many problems. -- This message was sent by Atlassian JIRA (v7.5.0#75005)