I'm sure there are situations where this would make sense to do, particularly if you're writing a small application, but in general I think it would be a bad idea.
You could apply any argument that you could make about global variables to static variables - they're still changeable anywhere in the application.
If your application (and dev team) is sufficiently large then you could easily have another developer accidentally update the default value without knowing the consequences.
If you were needing to create the objects using different default values - maybe you could take inspiration from the Factory Pattern, and have the code for specifying the defaults within the factory class so that different defaults could be used per instance. You could then go the distance and make your factory instances immutable so that you'd have to intentionally reassign references to it everywhere you wanted to use the new default value.
Though I think I may be suggesting over-engineering here.