hmm not sure if we really should add this.
This was certainly a good thing back at the time when we discussed this. But from trying to use CDI's own @ConversationScoped in a real world JSF project I must say - it doesn't work out. Reason is that our CDI Conversation is lazy-starting which is way too late for JSF applications. Because what happens if you have a mandatory field not set or any other JSR-303 or JSF validation issue? In this case your action - which would make the conversation long-running - just doesn't get invoked! So you end up with a standard @RequestScoped behaviour and your bean will over and over get created again with each view hit.
Also: CDI conversations doesn't prevent opening an action link in a new window or tab, which makes them unusable for multi windowed applications.
I guess the same reasons apply why CODI introduced an own ConversationScoped and why Seam3 also introduced an own one, right?
So, since the CDI @ConversationScoped is kind of naturally restricted, I'm not sure if it's really worth adding a complex management SPI for it.