Problem was solved for us when we add to the @Cache annotation on our entity the includes="non-lazy" property.
Non the less it is rather strange that the behaviour changed ....