Firmware 3.5 mk2 parameterMap.set triggers the control function even when there is no change

parameterMap.set triggers the control function even when there is no change. This behavior was different in 3.4, where the function was called only on a change.

Is this a feature or a bug? Hopefully it is a bug, because as a feature it will be a lot of code to verify that there was a change with a previous value!