Ways not allowed to combine, if belongs to different relations

[Plutoz]

There is two adjacent ways. Each of the them belongs to a different relation(a route=hiking and a route=bicycle).
In earlier versions of JOSM if I give the 'combine' command, the two ways merged and both of the relations stayed on the combined way.

Current problem: after give the 'combine' command a dialog appears with the conflicted tags, but the 'Apply' button is not allowed to push, nor after resolve all tag conflicts.

Screenshot:
​https://dl.dropboxusercontent.com/u/21225383/osm/josm%20comnine%20error.png

Example to demonstrate the problem:
​https://dl.dropboxusercontent.com/u/21225383/osm/ticket%2012252.osm

JOSM details:

URL:http://josm.openstreetmap.de/svn/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2015-12-29 02:12:28 +0100 (Tue, 29 Dec 2015)
Build-Date:2015-12-29 02:32:51
Revision:9207
Relative:URL: ^/trunk

Identification: JOSM/1.5 (9207 en) Windows 10 64-Bit
Memory Usage: 458 MB / 1804 MB (214 MB allocated, but free)
Java version: 1.8.0_66, Oracle Corporation, Java HotSpot(TM) 64-Bit Server VM
VM arguments: [-Djava.security.manager, -Djava.security.policy=file:C:\Program Files\Java\jre1.8.0_66\lib\security\javaws.policy, -DtrustProxy=true, -Djnlpx.home=<java.home>\bin, -Djnlpx.origFilenameArg=C:\Users\pluto\AppData\LocalLow\Sun\Java\Deployment\cache\6.0\31\583aa85f-78fc015b, -Djnlpx.remove=false, -Djava.util.Arrays.useLegacyMergeSort=true, -Djnlpx.splashport=63838, -Djnlp.application.href=https://josm.openstreetmap.de/download/josm-latest.jnlp, -Djnlpx.jvm=<java.home>\bin\javaw.exe, -Djnlpx.vmargs=LURqYXZhLnV0aWwuQXJyYXlzLnVzZUxlZ2FjeU1lcmdlU29ydD10cnVlAC1Eam5scC5hcHBsaWNhdGlvbi5ocmVmPWh0dHBzOi8vam9zbS5vcGVuc3RyZWV0bWFwLmRlL2Rvd25sb2FkL2pvc20tbGF0ZXN0LmpubHAA]
Dataset consistency test: No problems found

Plugins:
- HouseNumberTaggingTool (31772)
- OpeningHoursEditor (31772)
- contourmerge (1014)
- reverter (31772)
- turnlanes (31772)
- turnrestrictions (31772)
- utilsplugin2 (31772)

[Klumbumbus]

This should already be fixed in r9193, please try again with latest version.

If not fixed please add your status report, as asked on newticket.