Deployment.config: JCP should always ready value from system level properties file if it is locked

Tested OS : windowsXP( home and professional), linux redhat ADS, solaris10(sparc)
Tested Build : mustang b86, b87
Problem Description:
If property is specified inside the system level deployment.properties file, then under all conditions Java control panel should read the property value from system level deployment.properties file ignoring the value specified inside the user level deployment.properties file. But this is not happening always. Dumping of system properties by pressing "S" on the Java console always returns the correct values.

Steps to reproduce:
1) Install 1.6.0 on the system( on unix register the browser with this newly installed JRE build)
2) Create deployment.config under
on windows:
<Windows Directory>\Sun\Java\Deployment
e.g. on XP it will reside under C:\Windows\Sun\Java\Deployment
Enteries inside the deployment.config:
deployment.system.config=file:///C:/WINDOWS/deployment.properties
deployment.system.config.mandatory=true
on unix:
/etc/.java/deployment
Enteries inside the deployment.config:
deployment.system.config=file:///etc/deployment.properties
deployment.system.config.mandatory=true
3) Create deployment.properties(system level ) under C:/WINDOWS on windows and /etc on unix
with following enteries:
deployment.proxy.type=1
deployment.proxy.type.locked
deployment.proxy.ftp.host=scaweb1.sfbay.sun.com
deployment.proxy.ftp.host.locked
deployment.proxy.ftp.port=8080
deployment.proxy.ftp.port.locked
deployment.proxy.https.host=scaweb1.sfbay.sun.com
deployment.proxy.https.host.locked
deployment.proxy.https.port=8080
deployment.proxy.https.port.locked
4)Invoke JCP > General > Network Settings > Advanced
On "Advanced Networking Settings" window, you can notice that ftp and secure enteries are disabled and values are set to
"scaweb1.sfbay.sun.com" and "8080"
5) Click on "Use same proxy for all protocols", ftp and secure host and port values will disappear.
6) Set the http host and port value(or even leave it blank) to "webcache.sfbay.sun.com" and 8080. Save the changes(Apply and OK)
7) Invoke JCP again and this time On "Advanced Networking Settings" window, you can notice that ftp and secure enteries are disabled and values are set to
"webcache.sfbay.sun.com" and "8080". JCP is totally ignoring the ftp and secure values specified inside the system level deployment properties file.
8) Invoke browser and invoke Java console. Press "S" on Java console to dump the system properties. You can notice that it's returing correct values against deployment.proxy.ftp.host and deployment.proxy.https.host i.e. scaweb1.sfbay.sun.com specified inside the system level deployment.properties file
9) Remove the deployment.properties file(user level) from the deployment user home. Invoke JCP again this time it will read the correct values