As currently implemented, the ConfigurationBeanLoader throws an exception if the RDF model includes a property that the instance being created has no use for.
The original intent was to assist the administrator who wrote the RDF configuration file, by warning (forcefully) about an unused, possible misspelled property. However, the unintended result is that no triples can be used to describe a configured instance unless that instance itself acts on (or at least recognizes) those triples.
For example, if we were to annotate instances of IndexingUriFinder (used in the search indexer), our intention might be that the indexer framework should act on those annotations. As currently implemented, however, the IndexingUriFinder itself must at least acknowledge the annotations in order to avoid a runtime exception.
It's worth losing the current "warning" in order to permit greater flexibility. Further, this seems more in keeping with the AAA principle of RDF in general.