I too feel that this is a retrograde change.
It tries to fix a "problem" that is actually the proper responsibility of the users router DHCP server configuration = and doing so from the B2 side by trying to hang on to an IP by keeping a connection active is simply a "bodge".
Not to be negative about this, may I make a suggestion.
I believe it is possible to get a Client device (ie a B2) to "request" a fixed (or specific) IP number form a DHCP server, I believe the command is
"send dhcp-requested-address xxx.xxx.xxx.xxx;"
While on first ever bootup of a B2, it would not know the range of a LAN's IP numbers, after first IP assignment the IP number given could be saved by the B2 and (if a new "Advanced" B2 menu switch was set) could be made to ask for that IP
on subsequent boots or WiFi/Ethernet startups.
This wood not be 100% foolproof because during a downtime of the B2's connection, the IP number could have been DHCP assigned to another LAN device (that is why a "fixed" IP set at the router end is best), but
given that a house's LAN is not very active, I would expect that most of the time the requested IP number will be available.
Hope this helps.
Fred