Which Knockout.js Cleanup Method Prevents Observable Array Leaks?

Goal

Determine the most effective cleanup strategy for large observable arrays in Knockout.js when destroying views, ensuring no residual references remain.

Constraints & Uncertainty

Knockout 3.0‑3.4 exhibit different internal implementations of cleanNode() and ko.removeNode(). jQuery’s remove() does not trigger Knockout’s cleanup, while ko.removeNode() may leave orphaned computed subscriptions if not paired with explicit disposal.

Unresolved Decision

It is unclear whether a single call to ko.removeNode() suffices to release all memory associated with observable arrays, or if additional steps such as ko.cleanNode() or manual dispose() of computed observables are required.

Specific Questions

• Does ko.removeNode() fully clear observable array references in Knockout 3.4?
• Is ko.cleanNode() necessary when DOM elements are removed via jQuery?
• Which subscription disposal pattern best prevents computed observable leaks during view destruction?