1/ @PortletLifecycleScoped and @PortletRedisplayScoped :
It seems similar with the javax.portlet.actionScopedRequestAttributes container runtime options, i.e a portlet using @SessionScoped and enabling the scoped request attributes would provide a similar behavior.
Why should add a non spec compliant feature to do something similar ?
2/ managed object eventing :
In the proposal the event is sent by the portlet container impl between the portlet instance creation and the initialization of the portlet.
Such event should instead be managed by the context around the portlet container impl (i.e the LifeCycle object).
This is due to the fact that there is only one step in the current life cycle.
To better solve this problem, we need to break down the life cycle into two phases : create/start and stop/destroy with a new event sent.
This way the CDI listener can properly operate on the portlet instance between the created and the started phase.