@Steve Ebersole: Have you looked into the issue commented by Bart Vensegbroeck below? We have the same issue as he describes. As a workaround I implemented a MutabilityPlan, and used @Mutability. But this gives a dirty object on all updates, even though there were no changes. Is it a bug that Hibernate 6 does not give the same dirty results as before? Will this be fixed in newer versions? I think that this issue is critical, and needs to be fixed as soon as possible.