Neither can the user. Users cannot remember a unique password for every site they visit. That's just not realistic.
The simple fact is that unique-password-per-site does not scale. Password managers don't work well, either, because they can't be integrated into the common mobile browsers, and they frankly just require too much user intervention. (Sure, I'll install this plugin on every machine I use, plus the gimpy custom browser for my phone and tablet, and I'll use the app to cut/paste into other apps that need auth...)
We really need to big players to get together and build a system that works, and for them to all implement it properly and push 3rd parties to use it. BrowserID seems promising, but I haven't heard of any other big players signing on to implement and support it.
I'm not familiar with how you write a web-app to use FB authentication - how much does using FB auth obviate the need for you to worry about user credentials?
Use FB by all means, but don't fail the auth if the user declines the extras.
I can be diligent and yet one mistake can still expose the user's (hopefully salted and hashed) password. If there is a financial impetus for someone to find my mistake, they will spend the time looking.
As a side note, I'd love to hear how the hackers came to be in possession of 6.5MM LinkedIn passwords ... what mistake was made that allowed them to collect unsalted hashes in the first place?