Yesterday I asked Are GUIDs generated on Windows 2003 safe to use as session IDs? and the answer combined with combined with this article GUIDs are globally unique, but substrin
The short answer is, no guid's aren't sufficiently strong to generate session id's if you want to prevent session id guessing and cracking.
For the same reason why you wouldn't want to use a GUID as an AES key, you don't want to use them for any type of sensitive identifies.
A GUID works extremely well for what they are designed to be: A mathematically guarenteed unique ID to never repeat.
Even if cracking a session ID is only worth $1000, imagine if thats done 100 times. Now you're talking serious bling.
I know it's an easy way out to use GUID's but resist, and deal with the pain by taking the proper precautions to adequately secure your application. Your users will thank you.