Tested Build: Tiger M3 - Build 02

Description:
When removeSingleInstanceListener() method get called the single instance file created under the deploymnet user home should get removed, so that application will be considered as normal application.

In M3 build, the removeSingleInstanceListener() is not removing the single instance file created.

Steps to reproduce this bug:
Visit this location http://cheran.india.sun.com:8080/jawstests/si/homepage.html

1. Click on the "s1.jnlp". A Red coloured frame with a Add, Remove and Close button will appear
2. Click on the Add button, not you can see a message in console saying that the SingleInstanceListener got added.
Now you can see the unique SingleInstance file got created in the deployment user home.
3. Now click on the Remove button, a mesg will appear in the console that listener got removed. But the singleinstance file is still present there.
4 Now click on the "si2.jnlp", still application is considered as singleton

The actual expected behaviour is, after removing the listener the subsequent launch of the applicaion should be considered as normal application,
but here this is not happening.

I noticed this problem in the build (all platforms)
java version "1.5.0-internal"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0-internal-jdeploy_12_aug_2003_23_17)
Java HotSpot(TM) Client VM (build 1.5.0-beta-b14, mixed mode)

When the single instance file got removed manually the application got launched as a normal application.