Hi Togas;
I suspect that it might be a problem with the view. I did a test with this scenario and couldn't repro this issue. In my test, I cleared the textbox, did a save, and the corresponding nullable field shows null in both my view and the database.
My suggestion to debug this is to put a breakpoint inside your SaveChangesAsync callback and inspect the EntitySaveOperation.Entities argument.
You can download my test in the link below. I'm using the NorthwindIB database that comes with every DevForce installation. In my test, I'm modifying a Customer.RowVersion field which is a nullable integer in the model.
www.ideablade.com/friends/Silverlight_AddingDeleting.zip