I share a model and it turns out the semantics of a "contains" method when used with a Lazy Collection differs heavily from how it would be used with an Extra Lazy Collection because contains uses primary keys where as the contains method on this particular entity is written to use a natural key thru it's equals method.

I cannot statically simply change the association to Extra Lazy because that will break other code so what I'd like to do is leave it Lazy but having it work Extra Lazily when my code runs. Our code is the same code base but runs in different vm's so changing an association type dynamically does not affect them.