Conflict with addressfield

Since upgrading to beta 5 I have encountered an issue with field collections containing addresses from the addressfield module, where the field collection is set to allow for more than one value. I'm not sure whether this is primarily an addressfield module or a field collection module bug, as the issues I've encountered so far generally go without any logged error, either in php/devel or javascript. However, it happened after upgrading field collection, so I'm posting it here. Here's some of the things I've encountered:

• I'm often unable to save content where more than one field collection is being used (that is, after clicking "add another item"), and the field collection contains an addressfield. When this happens, the page refreshes on submit, however it returns to the content form without any displayed message as if nothing had happened.
• After clicking "Add another item" on the field collection, select options in the newly created addressfield occasionally freeze so that they are unable to be opened, but no javascript error is logged. When this happens the "Add another item" button also breaks, but content is able to be saved with the new field collection.
• "Add another item" sometimes creates a new entry with a blank addressfield, but often copies all of the information from the previous addressfield to make the new one. When it does this, the content can be saved with the duplicated information without any issue. However, changing this information in any way (including minor textfield changes) results in the content being unable to be saved, even if it is restored to be identical to the previous content.
• 'Add another item' often stops working past 3 fields, however this may be a separate issue.
• Using the remove button to delete a previously saved field collection often prevents the content from saving

I've tested addressfield with multiple values outside of field collection, and there doesn't appear to be any issues. Addressfield is itself a container that uses ajax to retrieve which input fields to use, so I'm thinking that there's some kind of ajax worm-hole going on here. There wasn't an issue with beta 4 though, so my hunch is it probably is fixable.