Why is switching an association to FetchType.EAGER globally not a real fix for N+1?

It eliminates the N+1 pattern for the one access path that triggered it, but now loads that association on EVERY load of the parent entity, everywhere in the application — including code paths that never needed it — trading one performance problem for a different, broader one that's harder to see.