Can't migrate ORPort options from 0.4.4.6 to 0.4.5.3-rc

Hello.

I was using unusual configuration for my relay: Relay was listening at public IPv4 address and private IPv6 address:

ORPort 443
ORPort [ipv6_address]:ipv6_port NoAdvertise

IPv6 address belongs to Yggdrasil network, but it actually does not matter. What important is that my IPv6 interface have no access to Internet.

This configuration was working fine with Tor 0.4.4.6.

But with upgrade to 0.4.5.3-rc, Tor begins to open not only IPv4:443, but also IPv6:443, which is, of course, then marked as unreachable.

I thought that it is possible to disable IPv6 listening at 443 port by modifying config this way:

ORPort 443 IPv4Only
ORPort [ipv6_address]:ipv6_port NoAdvertise

But then my log file began to be flooded with such messages:

Jan 22 15:55:04.000 [notice] Self-testing indicates your ORPort ipv4_address:443 is reachable from the outside. Excellent. Publishing server descriptor.
Jan 22 15:55:05.000 [notice] Guessed our IP address as [ipv6_address] (source: METHOD=INTERFACE).
Jan 22 15:55:05.000 [notice] Self-testing indicates your ORPort ipv4_address:443 is reachable from the outside. Excellent. Publishing server descriptor.
Jan 22 15:55:06.000 [notice] Guessed our IP address as [ipv6_address] (source: METHOD=INTERFACE).
Jan 22 15:55:06.000 [notice] Self-testing indicates your ORPort ipv4_address:443 is reachable from the outside. Excellent. Publishing server descriptor.
Jan 22 15:55:07.000 [notice] Guessed our IP address as [ipv6_address] (source: METHOD=INTERFACE).
...

Adding Address ipv4_address to torrc did not helped too.

Please let me know how to properly configure new version of Tor. Or fix a bug if it should work, but not working as intended.