I don mean u, dead sure u have lots of experience to have such a deduction, but for those have problem with ORMs or other tools and techs, there is a famous proverb, "A bad workman blames his tools". In software work, the design can make a product brilliant or bring it to the hell, which is highly ignored by us.

Just give u an example, when we use to implement our product using JDBC, we usually had a simple design and code  for handling a master-detail entity, and we are so flexible to implement it however we loved to depends on the scale  of the case.
Maybe if it was a basic info entity we made a selection on all records and filled the master-detail-entity, or we lazily loaded the details  (children) using a different biz method, or whatever, the same in saving data in DB.

Now ORMs simplize the persistence layer for example for this case, by its diferent relational mapping, BUT we should not forget an enterprise  project is so different comparing to a website or a small  project. You should not have a blind trust the implementation of technology vendors, and you have to count any cent on those kinf of projects.
Refering to my master-detail example, ORMs make that easy, but you must handle memory leaking, loading large  valume of data and lots of other pitfalls by choosing appropriate strategy in your analysis/desgin and the implementation.