In contrary to JSF managed beans, CDI managed beans are not stored directly by their managed bean name in the session map. They are instead stored in server's memory by the CDI manager implementation (Weld, OpenWebBeans, etc) using e.g. session ID as key.
The trick which you used there is therefore not applicable on CDI managed beans. You need to look for an alternate approach. The right approach in this particular case is to use @ConversationScoped
instead of @SessionScoped
. In properly designed web applications, there should never be the need to manually terminate a scope. So using @SessionScoped
for a conversation/flow was already wrong in first place.