Thanks for letting us know the reason behind this change, after discussion with our product specialists regarding this change in Weblogic its a lengthy process which involves so many changes it seems. So their suggestion is to raise an SR if it is your mandatory requirement, so that they can work on it.
Thank you for your interest, the issue has been resolved. The detail steps are in the SR, but include modifiy the plan.xml file, update to the tag <context-root> in weblogic.xml file into prweb.war. Additionally update to the tag <context-root> in application.xml file in ear file.
We're looking at the same thing for WebSphere and Tomcat. Does this solution just work for Weblogic or would updating the .ear file as per SA-54609 work for us too? (I would need to get resources to test this out - hence asking before I get in a long process of finding it out myself!)