What can be done about this - aside from the obvious act of me changing my password?
Password checkers aren't perfect and if someone wants to dedicate all their time to brute-forcing my password, enjoy, I could restore my journal from backups in about an hour. Plus, this would be a fairly detectable process: You'd see a lot of similar login hits from the same IP. Due to bandwidth shortages, it would be in the best interest of the LiveJournal folks to detect something like this and block the attacking IP. Thus, I do not desire to change my password.
This brings up another point: We need a different way of routing messages and errors in iJournal. The Console or a log file are two obvious places to send these messages. I find sheets reporting errors like this password warning very annoying and I would love to be able to turn them off (or better, reroute them to a move appropriate place.) Simply reporting "Error: See log file for details." in the status bar at the bottom of the main iJournal window and putting the full text of the error elsewhere could be an optional feature in the Preferences.