The Registry Fix Solved The Problem!
53 hours have elapsed, and during that time I have not needed to reconnect my Mavericks 10.9.3 client to my Windows 2008r2 server.
So, it appears that the registry "fix" solved the "Drop" problem.
Having said that, I haven't tested for potential
server connection resource exhaustion due to excessive stale sessions that may or may not be automatically closed by the server's resource management processes.
In my case, with only a few computers connecting to my server, that would probably never be an issue to reach critical mass. But, in an enterprise setting, it would be prudent to test for occurrence of stale sessions, and either tune the disconnect value to a real-world figure (not the FFFFFFFF recommended in the Microsoft KB article), to maintain connections for a reasonable period, but not the virtually indefinite period that Microsoft suggests, or manually track and close stale sessions.
Doesn't this sound a lot like managing a DHCP scope on an over-populated network with a lot of transient users?