sensboston, OAuth is a major step forward for user security. It does bother developers as it involves a "dirty" step in the authentication.
As a user, I just simply can't say how much I love OAuth. The only authentication I'll need to make is against the service that I registered my account with. With OAuth, I no longer have to provide my credential to yet another app, risking it being stored somewhere. I wish the OAuth providers (like DropBox and Twitter) try to make it so hard that no one can by pass the login by simulating the HTTP traffic. This way, my credentials is much, much more safe.
As a developer, it's dirty though, but once you weight the benefit of user, it's a great feature. For my application, I can guarantee user that my application no longer takes their password. Everything they do will be via the service they trusted. Zero risk of their credential being leaked.
One annoying thing I had with both SkyDrive, (I guess also apply to DropBox) was the "Remember my password" check box in the authentication page. Next time I display the authentication browser again, it automatically login, and I hated that.
You have multiple choices here:
1. When the browser is loaded, load the logout page first, which will definitely clears out the cookies. Don't try those cookies delete methods using javascript on the internet. Just show the log out screen, and once the page is loaded, cancel the page display and shows the login page. This will take less than half a second and works all the time.
2. In SkyDrive case, I think it can be a feature. The next time the authentication page is displayed, the browser remembers the cookies, so user doesn't have to login. Instead, SkyDrive will display the confirmation page again so that user can either tap on "OK" to trust our app, or click log out and then sign in using another credentials. I can't speak for the DropBox case as I've not tried it, but it's quite convenient for the user.
Hope this helps you calm down.