My MBP doesn't remember my Time Capsule wireless network when waking from sleep

Question

My MBP (OS 10.5.8) doesn't remember my Time Capsule wireless network when waking from sleep.  Thus, every time my MBP wakes from sleep, I need to select the Airport icon in the upper menu bar, select "Join other network", enter SSID and password.  This is very cumbersome.  And, I never had this problem when I was using the ISP's provided wireless router/gateway/DSL modem. Adding the Time Capsule and using it to generate the wireless network has introduced this problem. 
It appears that this problem has to do with the hidden SSID.  I don't need the lecture on how hidden SSID provides no serious security benefit.  That's why I have the WPA2 encryption.  I'm interested in a solution that will allow the Time Capsule to generate the wireless network, maintain a hidden SSID, continue to use WPA2 encryption, but have my MBP recognzie and autoconnect to this network.
Solutions I've alread tried:
1. Open Network Preferences
2. Select Airport from left hand column (and ensure Airport is at top of that list)
3.  Select Advanced
4.  Delete all Preferred Networks.
5.  Apply settings.
6.  Restart computer
7.  Return to Network Preferences and from Advanced page, manually add my network with hidden SSID and WPA2 password
This solution works fine as long as I don't take my computer elsewhere and connect to another network.  As soon as my preferred networks list gets another network, my MBP stops finding my TC network.  Since I take my laptop to a lot of places (it's a laptop, after all...) this is a problem.
As I say, prior to adding the TC on my network (and using it to generate the wireless network), my MBP had no problem keeping 50+ preferred network names/passwords in the Preferred Network list, but always automatically finding/connecting to my home network without the need to "Join other network."  Thus, I assume the problem lies with the Time Capsule.
Any ideas?

Answer 1

LaPastenague, thanks for weighing in.  Didn't know that the hidden SSID capability was not IEEE standardized, and thus different devices will handle hidden SSID differently.  With my admittedly limited knowledge of how SSID/hidden SSID works, I'm still a little confused as to why my MBP would remember the generic router/gateway's hidden network, but struggle with the TC's hidden network.
To my knowledge, when an SSID is broadcast by a base station (Airport, wireless gateway, etc.), a connecting device (like a laptop, iPad, etc.) detects this broadcast--this would be a passive reception of this SSID signal.
When an SSID is hidden, the base station does not broadcast its identification.  Rather, a connecting device must transmit the name, and when the base station recognizes the broadcast, the connection is made. That's what you do when you select "Join another network" and manually enter the SSID.
The idea with OS X's Network Preferences is that these steps, whether for hidden networks or broadcast SSIDs, become automated.
Where is the potential for a different chipset between the TC and the previously used wireless router/gateway to alter this functionality?  Shouldn't the selection of an SSID by the MBP to broadcast to seek for a base station be a function solely on the MBP?  And once broadcast by the MBP, the TC should detect and reply? 
Basically, the MBP can connect to the hidden TC manually just fine.  The MBP can connect to the old setup automatically just fine.  The MBP cannot connect to the TC automatically.  Aren't these automatic connection functions solely on the MBP?
I'll try un-hiding the network and re-verifying that the problem is exclusively with the hidden network.
Z