Disabling a feature does not release the claimed settings/components

When I disable a feature, I would expect that the settings of this feature can be set in another feature. However, I see:

drush en -y features_test
...
drush dis -y features_test
...
drush pm-uninstall -y features_test
...
drush cc all
...
drush fc '*' | grep Provided | grep features_test
 field:node-features_test-field_features_test                    Provided by: features_test
 filter:features_test                                            Provided by: features_test
 node:features_test                                              Provided by: features_test
 taxonomy:taxonomy_features_test                                 Provided by: features_test
 user_permission:create features_test content                    Provided by: features_test

Neither the UI nor drush let me export one of these settings to another feature.

drush fe features_test_2 filter:features_test
 No unexported filter components match "features_test"                [error]
 No components to add.                                                [error]

What I try to achieve is setting up an enviroment with a stage and a live site, each one controlled by a feature (plus another "common" feature included as dependency for both). But the issue described above makes it impossible have the same setting (e.g. variable:theme_default) set differently in the stage and the live site.

Is there something I missed, which makes it possible to clean up the "exported" status of components?