"unable to start application" / FileNotFoundException after webstart app is redeployed

I'm trying to deploy a webstart app and have problems with a changed jar module file name.

The app works fine when it is deploy for the first time but whenever I deploy a new version, I cannot start it via webstart anymore (FileNotFoundException). The reason seems to be the changed filename of the jar module.

glassfish-application-client.xml:

<glassfish-application-client>
<java-web-start-access>
<context-root>/my-client</context-root>
<eligible>true</eligible>
</java-web-start-access>
</glassfish-application-client>

application.xml:

<?xml version="1.0" encoding="UTF-8"?>
<application>
<display-name>My Client</display-name>
<module>
<java>${swing-app-module}</java>
</module>
<library-directory>lib</library-directory>
</application>

$swing-app-module is e.g. 'swing-app-1.0.jar' (set via maven)

Glassfish generates the following JNLP:

<jnlp spec="1.0+" codebase="http://localhost:8080/___JWSappclient/___app/my-client/"
    href="http://localhost:8080/___JWSappclient/___app/my-client/___dyn/lib/swing-app-1.0.jarClient/___main.jnlp">
...

For a new release, I increment the version number to 'swing-app-1.1.jar' and redeploy the EAR. When I try to start the app via webstart afterwards, I get the following Exception:

java.io.FileNotFoundException: http://localhost:8080/___JWSappclient/___app/my-client/___dyn/lib/swing-app-1.0.jarClient/___main.jnlp

Why does the URL of the JNLP points to a location inside the jar module? How can I keep webstart running (without removing the version number from the JAR) after a redeploy?