Hi Javier,
1. A generic recommendation is to create packages for semantically-related use cases. For example, session-related use cases (Log In, Log Out) User Maintenance (add/delete/modify/lock account/modify password). This way it'll be eaiser to read the diagram.
uhm... maybe i should read some more chapters in my uml book

2. Another recommendation is to use verb-noun approach for the use case names. This would change Login to Log In, Logout to Log Out and Load UserData to Load User Data, Modify UserPassword to Modify User Password, etc.--actually, login and logout, logon and logoff, are nouns, but people mistakenly uses them as verbs ;-)
hmmm.... i read it, but i did it not.
3. Administrator IS-A User, therefore, it should be a generalization of user, not backwards. This stems from the fact that most users are not administrators, while all administrators are users. This would also eliminate the Normal User actor.
i did another use case model and uploaded it to
http://www.aspintranet.de/uml/index.htm(please click on use case view / UserManagement)
4. Given the recommendation above, Delete User could have an extension point when the user is Admin, not when it is not.
i hope, i did the modification well.
5. I do not see how the Login use case includes Save UserData
i wanted to show, that if a user/admin is logged in, he/she may not be able to modify data. Or do you mean, that Save User Data could never be reached, before being logged in and have data loaded?
6. I do not see the reason for existence for Modify UserPassword and Modify UserName. It seems to me they do not contribute to the model and should be part of Modify User.
i thought, it needs to be shown seperatly depending on the user state (admin/normal user) - seems to be not so

If the newer version is still not correct, you can also edit the new model at
http://www.aspintranet.de/uml/aspintranet.eapthanks for all your tips on UML

regards,
Alex