Same for me, I have been confused while encountering this API inconsistency and was also very surprised not finding more discussions about it.

However, it seems that the issue has now been fixed in the last JPA specifications (3.2), as visible in the javadoc here.