In WPF, the RoutedUICommand is not a dependency object, nor does it implement INotifyPropertyChanged meaning if you were to bind its Text property to something in the UI such as a MenuItem's header, and Mode wasn't OneTime, you'd potentially get a memory leak with dynamically loaded context menus or UIs where items get created and destroyed very frequently as those UIs are loaded and unloaded.
Conversely, if you do use OneTime, you'll avoid the leak, but you'll lose change notification which we need as our menu's text needs to dynamically update as per status in the application. (Think how a typical "Save 'xxx' As..." command changes to reflect the current item's name.)
That said, how do we properly bind to text and get the changes without causing memory leaks?
Our proposed solution is to create a subclass of RoutedCommand (note: no 'UI') where we create our own Text property as well as implement INotifyPropertyChanged to support it. However we're not sure if there will be issues with WPF's built-in support for things like automatically binding a MenuItem's header to the Text property since it isn't a RoutedUICommand. (Note, we could just use a real RoutedUICommand object, then 'new over' the Text property but there you can run into issues with how you access the property so we'd rather avoid that if possible.)