So I updated to 10.9.3, mind you that I had to get the wifi connected at home in order to do that right, which is done by toggling it off and on (regarding the stuck-wifi-on-wake issue).
After installing and rebooting into 10.9.3 (from 10.9.2) my Lat 2013 15" retina mac book pro did not reconnect to wifi. I again tried pinging the router locally, with no link, saw it thought it was connected to the ssid I have, and it got no traffic through for some 10-15 minutes until I rebooted.
I didn't zap pram, change settings, clear the smc etc. Just rebooted, and now with 10.9.3 which had that initial disspointment, it connected on bootup. And it has continued to reconnect every time I sleep and wake.
However I have not since rebooted again. Current up time (during which I've slept and rewoken about 3 times for 4-20h at a time depending, is 4 days, 12h and 15 minutes. I am affraid to reboot, or change any network settings, since, well, there's a chance it could behave again as it did on first boot, with the stuck-wifi-on-wake issue.
The only thing that's changed in the wifi details is:
CoreWLAN went from 4.3.2 (432.47) to 4.3.3 (433.48).
This might control how the driver is told to sleep and wake. It might not. That's a guess.
The other details are the same between 10.9.2 and 10.9.3: CoreWLANKit, Menu Extra, System Information, IO80211 Family, Diagnostics, AirPort Utility, All the details including Firmware Version on en0.
The router was not changed nor restarted during this.
I'll set a date for a couple months from now to remind myself to report back if stuck-wifi-on-wake has not recurred. If it has, I'll let you know sooner.
P.S. dantart, you have more networks than a single 100mbits fibre network. One of those networks is your 802.11n network you're using with your macbook, another may be the 1gbit wired network your router bridges your wifi network to which you may not be using, and your router routes packets to your 100mbits fibre network connection. Your wifi will never be capable of 1300mbits becasue that's an 802.11ac spec, but all people are saying is that were you using an 802.11ac network you should expect to get that speed because that's what you were promissed in the specifications of the machine you bought... personally I take issue with what they were saying too becasue no one gets the max speed in practice. We know that you're not seeing those speeds, nor the 600mbits max capable of your 802.11n network. We don't know for sure if it's congestion or interference on the wifi, the router, or the fiber connection to the internet. Those tests are never quite reliable. But we do see that yes, you've tested two different devices around a similar time, multiple times, and on average yes your older macbook is working better than your newer one, and it's probably totally down to the wifi network. I think the only question is what can anyone but Apple do about it? And some suggested some kind of consumer advocate suit process. Which is close to being able to do nothing.