Deletion of Image in translation ignored

This problem is present also in beta1 version (on image fields and on more generic file fields).
If you remove all instances of attachments (files) on a translated version, system shows you the files of the source version! (instead of nothing)
I don't think this behaviour is by design.

You need to use at least Drupal 7.15. Please update and see if the problem still exists...

Yes, I have installed drupal 7.16 on my online site (and latest dev for entity translation), but this problem is still present.
I'll test this on a fresh local install of drupal 7 later, and I'll post results!
Thanks anyway

I have tested this problem on fresh Drupal 7.16, last entity API dev, last entity translation dev.
These are the steps to reproduce the problem:
1) configure a second language and enable url detection of language (ita)
2) add a file field to a taxonomy vocabulary with unlimited values and with translation enabled
3) create a taxonomy term A_eng and upload two files a.txt and b.tx and save
4) create a translation for term A_eng (named A-ita) and save; on this form you can see a.txt and b.txt and you can associate a translated description and so on (and this works well)
5) edit A_ita and remove one file from A_ita (es. b.txt) and save; if you view A_ita page you see only a.txt as expected
6) edit A_ita and remove also a.txt (so there are no files on this translation) and save; if you view A_ita you see a.txt and b.txt (but I expect to see nothing because I have removed all files for A_ita translation)
It seems to me that when the number of files of a translation is 0, the system suppose that the translation is in sync with the source and so it shows the attachments of the source (instead of no attachments).
This test is made on total fresh and very small installation (not even i18n & co is installed).
Thanks again

Ah okay, this is actually by-design: When a field appears to be empty (i.e. not translated), then the value of the original node is displayed instead. This is an option which is enabled by default, but you can disable it on the ET settings page (Untick "Enable language fallback ").

Does that fix it?

This works the same with other fields, it's not specific to file-fields or images.

You're right. If I disable language fallback, it works like expected. But I think this behaviour is not really reasonable (at least not if it can't be configured at single field level).
An empty field doesn't mean that this field isn't translated (not always). For images and files at least, it's possible that for some reason a translated content has't attachments (for example because this files/images/contents are not yet ready).
Do you think this strange behaviour can be improved/changed on future releases of entity translation?
Thanks a lot!