SlingServerRepository configuration change - expected behavior?

[Rory Douglas]

If I select the SlingServerRepository configuration in the webconsole ( 
the .2423424etc configuration, not the factory configuration), change a 
property (in this case, max idle sessions) and click "Save", I see a 
second configuration gets created ( .44534534etc), and I start seeing 
workspace lock errors from the RepositoryPinger.

I can fix this by just deleting the old configuration, but is this 
expected behavior or a bug? I would expect this kind of behavior when 
clicking "Create" on a factory config only.

Regards,
Rory