Disable Envers for a specific deployment

Issue

User uses a common domain model for a number of different deployments and would like to activate auditing with Envers for some deployments and not for others.

It appears though, that as soon as user add @Audited annotations to domain entities, Envers is automatically picking those up and looks for the tables that are required for logging. Is there a way to disable Envers in persistence.xml for some deployments? In previous versions it had to be enabled explicitly by adding EJB phase listeners to persistence.xml.