Hello,

This issue can be closed.
In fact the behaviour seems normal since the object accused of eager loading was already cached in the session du to a prior query.