I don’t think that we changed anything since 3.1.0 that may cause this behavior to change. But I may be wrong. I don’t know!
Are you sure the request scoped bean is re-created? Perhaps some component explicitly sets the properties to null? You could check this by adding a log output to the default constructor and the property setter.
Is your request scoped bean managed by JSF or some other container like CDI/Spring?
Do you play Magic?
Get TopDecked MTG, the #1 Magic App, built by players, for players. Free to use, forever.