I've got the following problem:
allthough the end-conversation-state of the pageflow is reached the @Destroy-annotated method of the seam component (plain java bean) of the terminated conversation is never called - a new conversation however (including a @Create-annotated method) is created just as designed. However, when the vm shutsdown the @Destroy-method is finally called for all out-of-scope component-instances created so far.
We're using SEAM 2.0.0 BETA 1 + facelets + trinidad + richfaces + JBoss 4.2.0.GA1
the following has to be added:
after session timeout (as config. in the web.xml ...) the destroy-method is called too ...