Dynamic reconfiguration: New participant server opens wrong ports

Starting from a stable 3-member quorum:

server.1=localhost:2801:3801;2181
server.2=localhost:2802:3802;2182
server.3=localhost:2803:3803;2183

I then kill server 3, clear its data directory, keep its myid=3 and change
its static configuration to

server.1=localhost:2801:3801;2181
server.2=localhost:2802:3802;2182
server.3=localhost:2804:3804;2184

Now what I would expect is that this "new" server 3 will not join the
quorum since the ports don't match what the servers 1 and 2 expect.
However, it can join. The problem is that the "new" server 3 does not
respect its configuration. Its logs will contain the new port number 2184,
but it will actually pick up the dynamic configuration offered by the
quorum and open up the old ports 2183 etc. After joining again, the dynamic
configuration file for server 3 contains

server.3=localhost:2803:3803:participant;0.0.0.0:2183

Also, echo conf | localhost 2184 never replies but echo conf | localhost
2183 returns

server.3=localhost:2803:3803:participant;0.0.0.0:2183

Is this actually intentional or a bug?

Best,
Niko Vuokko