When using the dynamic swatches example in showcase (there are three examples for ace:colorEntry-> Swatches each in a tabPane, the dynamic example is in the third or last tabPane):-
choose up to 4 colors and click on CreateSwatch button.
a new colorEntry component appears with the Swatch created from the up to 4 input colorEntry components previously.
Choose a color and it shows the selected color as it should.
Click on "Reset" button and perform the same steps again (choose different or more or less colors but make sure the color is different than the last one chosen or the value change will not fire!)>
Create new swatch
Now choose a color from the new swatch created and a response containing the update returns from the server and not only is the ace:colorEntry component updated, but a duplicate is created too.

I'll attach an screenshot, but tried, ace:tabPane cache="none" as well as various attributes on the ace:tabSet. Tried tabSetProxy with forms within the tabSet, ace:ajax with various execute and render values. Replaced c:forEach with individual components.....
still get the update duplicated into the client.

After commenting out the ace:tabSet and ace:tabPanes, I was able to reproduce the same issue. After reload of the page, the duplicate disappears.... leading me to wonder if the original markup should be destroyed before a re-render can occur in some cases by the javascript(?)