When a control point is disabled or reconfigured the control point's data is freed. If no other thread is using this data it can be freed immediately in the disable or reconfigure operation. If another thread is executing using this data it cannot be freed until the thread using it finishes using it.

Until this is implemented this memory, if not freed immediately, is left allocated at shutdown. This is a memory leak.

The memory leak described above is OK for the POC. Finish implementing this for the MVP.

When the concurrency problem of WT-13541 is analyzed it might be found this reconfigure API is needed. If so, this becomes part of the POC instead of the MVP.

Note, the control points implementation tickets are in three time periods:

1. POC - Part of the POC.
2. MVP - Part of the minimal viable product. However, even the POC can be used but less conveniently than the MVP.
3. Future - Enhancements after the MVP.

The title of each ticket starts with the time period.

Status: Most of this is implemented already: the locks and reference counts needed. What is not there yet is freeing any still allocated memory at shutdown.