It does not matter if using fetch type EAGER for mappings is an anti-pattern or not. There are situations where you have no chance to alter that behavior. The specification allows that anti-pattern state and I guess that's the reason why those load graph adjustment feature has been added. I tried hard to not load those EAGER attributes since hours and since I discovered this ticket here. IMHO this javax.persistence.fetchgraph hint feature is useless with your decision to use that section-3.7.4-provider-can-load-additional-data-loophole.

To sum it up: +1 for not loading missing entity graph attributes although marked as EAGER. And BTW thanks for your hard work