I've found that the functions in FieldSet that manage which fields are in the fieldset have a variable behavior: some are recursive (the field can be "buried" in a composite field, e.g removeByName, addFieldToTab) and some others aren't (e.g insertBefore/After). I need these ones to be recursive and i've changed my local code to fit this, but wondered if there is any special reason to avoid recursion here.

Bernat: I've flicked Sam an email for his opinion on this, but as far as I believe, there's no reason that these don't recursively look inside composite field types for more fields.

Sam may be able to shed more light on this.

This should be fine...