After doing some research online for the WWW custom domain name issues. I found a helpful link with some information about deleting the "A" record in the DNS control panel of Godaddy for your domain name.
Google Custom Domain - Case Study #1In this article (actually the comments) was a reference to removing the "A" Record. After removing the "A" record, now everything seems to point to the same location.
Keep in mind, whenever you do changes at the DNS level, it can take sometime before things propagate online.
The interesting thing is that I actually had to set up two CNames Records. One just with the straight www and the other with www.wednesdays.ws both pointing to ghs.google.com. I tried deleting the www.wednesdays.ws = ghs.google.com but then things did not function at all. I tried deleting both and starting over with just the www = ghs.google.com. No change, still did not function. I then went back to both. See below.

WWW Wednesdays WS DNS Custom Domain Name
In addition to the above settings, my Blogger settings for publishing are to have the blog published at www.wednesdays.ws and using the built in redirect forward of the Blogger engine, I set wednesdays.ws to go to www.wednesdays.ws. See below.

Custom Domain Name Settings For Blogger With Wednesdays Website
Everything seems to be functioning properly with the custom domain.
Here is an example of what I am talking about for proper redirecting and forwarding:
http://www.wednesdays.ws/2007/02/meet-jim-on-internet.html goes to Meet Jim on the Internet article. Before the removal of the "A" record the following without the "WWW" http://wednesdays.ws/2007/02/meet-jim-on-internet.html would go to the root level or
www.wednesdays.ws. After the change,
http://wednesdays.ws/2007/02/meet-jim-on-internet.html goes to the same location, but adds the "WWW" in front of the address. This is perfect, because no matter which way you have links to your website, they will always go to the correct location.
Hopefully, this will hold up, as a viable solution to the "WWW" Custom Domain Name problem.
Spoke too soon. There seems to be a difference between Firefox and Internet Explorer, in the way the non WWW is handled. It works on three computers with Firefox but with the same three computers it doesn't function in Internet Explorer.
More research required.
PS Meet
Jim on the Internet.