The default value is only applied to registration. This is because we know for sure the user never supplied a value to the field. We've plans to implement support for a default value for registration (or just apply existing default value parameter to everywhere) in a future release. Best I can suggest is to try and force a default value to be stored in the users profile using CB Auto Actions by acting on the after user registration trigger so when they register those fields are given a value anyway.