Installed Studio released packages are locked by Windows and not removed by update center

Problem is reproduced when downloading a studio package that appears as a release of the Studio configuration, while anotherone is already installed. In that case, the package will be installed and loaded, but the previous jar won't be removed, thus causing problems at next server startup.

the system should persist the list of jars to remove before really starting the server next time.

Reproduced on Windows Server 2008