Yes, we removed Jaxen (and dom4j) from the Ivy project classpath with version 7.2.
Unfortunately, just including Jaxen and dom4j in the project then causes the error described by you. This is because we still need to include dom4j as part of our Hibernate library, and this version has priority over the version in an Ivy project.
As a workaround, you can create an Eclipse plugin with your Jaxen library that is an Eclipse 'buddy' of our Hibernate library.
We have a demo project for exactly that, you pretty much just need to adjust the library version:
See the README.md in the extension-demos repository on how to build and install your own plugins.
Hope that helps,