This behaviour is still present in Hibernate and Envers v5.0.2. It can be reproduced using the attached testcase