Seam eliminates the JSF managed bean. That's part of the idea of the glue code that Seam is for bridging JSF and EJB. The JSF directly calls the session bean public methods via the local interface and expression language (EL) in the xhtml.
If a temporary conversation is promoted to a long-running conversation via @Begin, it will either timeout or be demoted to a temporary conversation after the @End method is executed and then destroyed after the render response JSF life cycle phase. If the @End method is not executed on a LRC, then that is considered an abandoned conversation (which will eventually timeout or be destroyed if the session is destroyed or times out).
@End instructs Seam to convert the long-running conversation to a temporary state after this method is invoked successfully.
There is a beforeRedirect attribute for @End:
If set to true, instructs Seam to terminate the temporary conversation prior to issuing a navigation redirect. The default is to propagate the conversation across the redirect and terminate it once the response is complete. Default: false.
Event = request scope
Page is in JSF component tree.
Conversation is subset of session (think multi-page wizards or shopping cart use cases)
Session is session
BPC is business process context for workflow/BPM use cases
you will usually use conversation, event, page, session scopes.
read Seam in Action, good book.