SQLAlchemy loads unrelated cached objects when using contains_eager

Question

I\'m using the contains_eager functionality of SQLAlchemy and I\'m seeing strange behavior when objects are already loaded in an existing session. Specifically,