No, it was not introduced because of a JPA releated problem.
- Build an additional sans-externalized jar that doesn't contain the externalized resources when externalized resources is true
- Include this jar in the script classpath, and exclude the normal jar, when externalized resources is true
Original this feature had nothing to do with JPA at all. Introducing and enabling it by default by setting externalizeResources=true caused problems with JPA, that's why it's recommended to set it to false again when using JPA, so you get the same behaviour as before the feature was introduced.
Hope that answers your questions.
Matthias